Dears, reading from your previious support request, I understood i should catch the server event transfer-destination-request to intercept the trasnfers of agent to another into a squad so that i can appl changes on second agent id necessary. If i understood correctly i hsould have: agent a--> getting informaiton (name, info, others) agent a --> transfer the call server event--> transfer-destination-request --> update agent b wiht the info of the customer or with other info by reshaping the content of the history--> patch squad agent b -> starts with updated information But transfer-destination-request is not triggered even if set into squad ( neither into assistant and into squad) Basically i would like to mimic the behave assistant-speaks-first-with-model-generated-output, but having the possibility to manage bettere the transition Thanks

@estrososcreed Hello! It seems like you have a good grasp of the process you'd like to implement for transferring calls within a squad. To ensure that the

transfer-destination-request

event is triggered and you can update the second agent (Agent B) with the necessary information, let's go through a few steps: 1. **Check Event Subscription**: Ensure that your system is subscribed to the

transfer-destination-request

event. This subscription is crucial for the event to be recognized and handled. 2. **Event Handling**: Once subscribed, you need to have an event handler in place that listens for the

transfer-destination-request

event and performs the necessary actions, such as updating Agent B with the customer's information. 3. **Patch Squad**: If the event is triggered but the information isn't being passed correctly, you may need to review how you're patching the squad with the updated information. Ensure that the patch operation is correctly formatted and executed. 4. **Testing**: Test the entire flow from Agent A transferring the call to Agent B receiving the updated information. This will help identify any gaps or issues in the process. If you're still facing issues with the

transfer-destination-request

event not being triggered, it might be necessary to look into the configuration of your squad and assistants to ensure everything is set up correctly. For the behavior you're trying to mimic, similar to

assistant-speaks-first-with-model-generated-output

, you'll want to ensure that the transition is smooth and that Agent B has all the context needed to continue the conversation seamlessly. If you need further assistance with the specifics of setting up the event or patching the squad, please provide more details or ask support for more info on this.

@Vapi i setup transfer-destination-request into the agents A and B i am testing, using the web interface tool. No luck because the event is not fired into the server

@estrososcreed I understand that you're experiencing issues with the

transfer-destination-request

event not being fired. Here are a few troubleshooting steps you can take: 1. **Configuration Check**: Double-check the configuration of both Agent A and Agent B to ensure that the

transfer-destination-request

event is correctly set up in the web interface tool. 2. **Permissions and Roles**: Verify that the agents have the necessary permissions and roles that allow them to trigger and handle transfer events. 3. **Event Conditions**: Review the conditions set for the

transfer-destination-request

event to make sure they are being met during the transfer process. 4. **Logs and Debugging**: Check the server logs to see if there are any errors or warnings that could provide more insight into why the event is not being triggered. 5. **Documentation**: Consult the documentation for the

transfer-destination-request

event to ensure that all prerequisites and configurations are met. 6. **Support**: If after these steps the event is still not being triggered, it may be necessary to contact technical support for further assistance. They can provide more detailed guidance and help identify any potential issues with the server or the event system. If you have access to any error messages or logs that provide more information on the issue, please share them so that we can assist you better. If not, and you've already tried the above steps without success, it might be best to reach out to the technical support team for further investigation.

@User is there anyt addtional configuration I should check to let the server to fire this event?

@estrososcreed Your new approach to store customer information by updating the squad before transferring the call from Agent A to Agent B seems like a solid plan. Here's a summary of the steps you're taking: 1. **Store Customer Information**: Agent A uses a tool named

storeCustomerInfoCall

to store customer information. This tool internally calls the squad patch API with the content of variable names and receives a 200 OK response from the API, indicating that the operation was successful. 2. **Tool Response**: The tool then responds back with a 200 status and a message "Customer Info Stored," confirming that the customer information has been successfully stored. 3. **Transfer Call**: After storing the customer information, Agent A transfers the call to Agent B. To ensure this process works smoothly, make sure that: - The squad patch API is correctly updating the squad with the necessary customer information. - Agent B has access to the updated squad information upon receiving the transferred call. - The transfer process is correctly configured to maintain the context and history of the call. If you've already implemented this and it's working as expected, that's great! If you encounter any issues or need further assistance, please let me know, and I'll be happy to help. If there's anything specific you'd like to test or confirm, please provide the details, and we can proceed from there.

@Vapi i have problem since AGENT B is not using the new values

@estrososcreed I'm sorry to hear that Agent B is not using the updated values after the transfer. Let's go through some steps to troubleshoot this issue: 1. **Verify Squad Patch Success**: Confirm that the squad patch operation performed by

storeCustomerInfoCall

is indeed successful and that the correct values are being stored. You can do this by checking the response from the API and ensuring that the data is correctly updated in the squad. 2. **Check Variable Accessibility**: Ensure that the variables updated by Agent A are accessible to Agent B. Variables should be stored in a shared context that both agents can access after the transfer. 3. **Timing of Transfer**: Make sure that the transfer to Agent B is happening after the squad patch operation has completed. If the transfer occurs too quickly, the updated values may not be available to Agent B in time. 4. **Review Transfer Process**: Examine the transfer process to ensure that it's designed to maintain the context and pass along the updated information. There might be a step missing that is necessary for Agent B to access the new values. 5. **Test and Debug**: Conduct tests to see if the updated values are being used by Agent B at any point during the interaction. Debug logs can be helpful to trace the flow of data. 6. **Documentation and Support**: Review any available documentation on the transfer process and variable handling to ensure you're not missing any configuration steps. If the documentation doesn't resolve the issue, consider reaching out to technical support for assistance. If you've checked all of these and the problem persists, it may be necessary to look deeper into the system's configuration or to seek assistance from the platform's support team. Please let me know if you need further guidance or if there's anything else I can do to assist you.

@Vapi this is theesponse from squad patch api https://cdn.discordapp.com/attachments/1289682322228252733/1289903285741813821/patch_respons.txt?ex=66fa838c&is=66f9320c&hm=3a0fdfbbe612ee33a315a74ecfb94139c02874313b07ed032bc0d29d1b63562a&

@estrososcreed It seems like you were about to provide the response from the squad patch API but the message may have been cut off. To assist you further, I would need to see the actual response from the squad patch API to determine if the operation was successful and the data was correctly updated. If you have the response, please share it here. Make sure it includes: - The status code (e.g., 200 OK) - Any relevant response body that confirms the update - Any error messages if the update was not successful With this information, I can help you troubleshoot why Agent B might not be using the new values after the transfer. If you're unable to share the response due to privacy or security concerns, please review it to ensure that the patch operation was indeed successful and that the correct data was updated. If everything looks correct on your end but the issue persists, it may be necessary to reach out to the technical support team for your API or platform for further assistance.

@Vapi this is json response from squad api

@estrososcreed It seems there might be an issue with the message transmission, as I'm not seeing the JSON response from the squad API that you're referring to. To assist you effectively, I would need to see the actual JSON response. If you're able to provide the JSON response, please ensure that it includes the following: - The HTTP status code (e.g., 200 OK) - The response body, which should indicate the result of the patch operation - Any messages or data that confirm the squad has been updated with the customer information Please paste the JSON response here, ensuring that any sensitive information is redacted for privacy and security reasons. If you're unable to share the JSON response or if there's a technical issue preventing the message from being displayed, you may need to troubleshoot the API response directly in your environment or reach out to the API provider's support team for further assistance.

@Vapi could someone from support to assit me?

@estrososcreed I'm here to assist you as best as I can. If you're looking for more in-depth support or if the issue requires access to your system's backend or detailed logs, it would be best to contact your platform's technical support team directly. For immediate assistance here, please provide any error messages, the JSON response from the squad patch API, or specific details about the problem you're facing. If you're unable to share these details or if the issue is too complex to resolve via this chat, reaching out to your platform's support team will be the next best step. They will have the necessary tools and access to provide you with the support you need. If you need help contacting them or if there's anything else I can do to assist you within the scope of this conversation, please let me know.

@User coul you help me with a call?

use assistantOverride property

@Sahil thanks for answer, unfortunaltey i'ts not working. I ma currently using a setup that from twilio calls make.com where i am sending a patch request to squad api To make it short, for any agent i put "assistantOverrides": { "serverMessages": [ "end-of-call-report", "transfer-destination-request" ], "variableValues": { <>} }, But It seems to not working What i noticed with assistantOverrides and patch requests is that it doesn't seem to be really effective. Using only variable name as refereence sometimes the next agent will know the name, some ohter not.

@estrososcreed can you share the recent call id.